Service operation chaining

ABSTRACT

For a multi-tenant environment, some embodiments of the invention provide a novel method for forwarding tenant traffic through a set of service machines to perform a set of service operations on the tenant traffic. In some embodiments, the method performs a classification operation on a data message flow of a tenant, in order to identify a set of service operations to perform on the data message flow. For some data message flows, the classification operation selects the identified set of service operations from several candidate sets of service operations that are viable service operation sets for similar data message flows of the tenant. In some embodiments, the classification operation is based on a set of attributes associated with the data message flow (e.g., five tuple identifier, i.e., protocol and source and destination ports and IP addresses).

BACKGROUND

Middlebox services have historically been hardware appliances that areimplemented at one or more points in a network topology in an enterpriseor a datacenter. With the advent of software defined networking (SDN)and network virtualization, traditional hardware appliances do not takeadvantage of the flexibility and control that is provided by SDN andnetwork virtualization. Accordingly, in recent years, some havesuggested various ways to provide middlebox services on hosts. Some havealso suggested accessing middlebox services in different clouds (e.g.,different datacenters of different cloud providers). However, currentservice chaining solutions are not as robust as they should be to takeadvantage of the heterogeneous middlebox offerings today.

BRIEF SUMMARY

For a multi-tenant environment, some embodiments of the inventionprovide a novel method for forwarding tenant traffic through a set ofservice machines to perform a set of service operations on the tenanttraffic. In some embodiments, the service machines can be standaloneservice appliances or computers, and/or service machines (e.g., virtualmachines, containers, etc.) executing on host computers along with otherservice machines and/or tenant machines. Also, in some embodiments, oneor more of the service machines are middlebox service machines thatperform middlebox service operations, such as load balancing operations,firewall operations, intrusion detection operations, intrusionprevention operations, encryption/decryption operations, etc.

In some embodiments, the method performs a classification operation on adata message flow of a tenant, in order to identify a set of serviceoperations to perform on the data message flow. For some data messageflows, the classification operation selects the identified set ofservice operations from several candidate sets of service operationsthat are viable service operation sets for similar data message flows ofthe tenant. In some embodiments, the classification operation is basedon a set of attributes associated with the data message flow (e.g., fivetuple identifier, i.e., protocol and source and destination ports and IPaddresses). This attribute set in some embodiments just includes thedata message flow's layer 2-4 header values (e.g., five tupleidentifier, i.e., protocol and source and destination ports and IPaddresses). In other embodiments, however, the attribute set includesother contextual attributes related to the data message flow, such asthe data message flow's traffic type (i.e., the type of content carriedin the data message flow), QoS ratings, layer 7 parameters, processidentifiers, user identifiers, group identifiers, etc.

In some embodiments, the service operations in the identified set ofservice operations have to be performed according to a particularsequence. To express the sequential nature of these service operations,the identified set of service operations is referred to below as theidentified chain of service operations. After identifying the chain ofservice operations for the data message flow, the method in someembodiments embeds the identified chain of service operations in tunnelheaders that it uses to encapsulate the flow's data messages. Also, insome embodiments, the method embeds in the tunnel headers a tenantidentifier (e.g., embeds a VNI, virtual network identifier) to specifythat the data messages are associated with a particular tenant (e.g.,are emanating from a machine of the particular tenant). The method sendsthese encapsulated messages along a tunnel to a first service machinethat performs a first service operation in the identified service chain.

The method in some embodiments identifies the service chain, and embedsthis chain in the tunnel header, by identifying and embedding a set ofnetwork addresses (e.g., destination IP addresses) of a set of servicemachines that are to perform the service operations in the chain. Insome embodiments, the method embeds in the tunnel header a serviceoperation descriptor (e.g., tag) for each service machine identified inthe tunnel header in order to explain the type of service operation thatthe service machine performs. In other embodiments, no such descriptoris embedded in the tunnel header. Also, the method in some embodimentsembeds a service index value in the tunnel header that identifies one ofthe embedded network addresses as the network address of the “current”service operation. As further described below, this index is used insome embodiments to identify the next service machine for performing thenext service operation in a service chain.

In some embodiments, the service machines addressed by the networkaddresses embedded in the tunnel communicatively connect to servicenodes that are connected to each other through a set of tunnels. Servicenodes can be different types of network elements in differentembodiments. For instance, in some embodiments, the service nodes can be(1) host computers on which the service machines execute, (2) standaloneforwarding elements connected to the service machines, or (3) serviceappliances that perform both the service node functionality (to connectto other service nodes via tunnels) and the service machinefunctionality (to perform one or more service operations). Also, in someembodiments, one service node can connect to two or more servicemachines in the identified service chain.

Accordingly, after identifying the service chain for a data message andencapsulating the data message with a tunnel header that contains thenetwork addresses of the service-machine set that perform the serviceoperations in the identified service chain, the method in theseembodiments passes the encapsulated data message along a tunnel to aservice node that communicatively connects to the first service machinethat performs on the data message the first service operation in theidentified service chain. In these embodiments, the embedded networkaddresses of the service machines define a service function path (SFP)in the tunnel header. This SFP along with the service nodes (connectedto the service machines on the SFP) and the tunnels that connect theseservice nodes define a service function chain (SFC) for the data messageflow.

At each service node along the SFP, including the service node thatconnects to the first service machine, the service node inspects thetunnel header and determines that the received data message is addressedto a service machine communicatively connected to the service node. Theservice node makes this determination in some embodiments by extractingthe service index from the tunnel, using this index to retrieve thenetwork address of the current service machine that has to perform theservice operation, and then determining that this service machine is onethat is connected to the service node.

Once a service node determines that the received data message isaddressed to one of its associated service machines, the service nodethen removes the tunnel header (i.e., decapsulates the received datamessage), stores information (e.g., the SFP and service index) from thisheader in a connection storage for later reuse, and provides the datamessage to the identified, connected service machine for processing. Asfurther described below, the stored information in some embodimentsincludes information for the service node to re-assemble the tunnelheader if it needs to re-encapsulate the data message after it has beenprocessed by the service machines, in order to forward the data messageto another service node.

Once the service machine performs its service operation on the datamessage, it returns the data message to the service node. In some case,a service machine might instruct the service node to drop the datamessage based on its service operation. In some embodiments, a servicenode might be connected to two or more service machines that perform twoor more successive service operations in a service chain. In such acase, the service node provides the data message (in its currentdecapsulated state) to the next service machine (connected to theservice node) in the service chain, after receiving the data messagefrom a prior service machine in the chain (assuming that the priorservice chain did not drop, or instruct the service node, to drop thedata message). In some embodiments, the service node determines that thenext service machine is also connected to it after receiving the datamessage from the prior service machine connected to it. In otherembodiments, the service node makes this determination before passingthe data message to any service machine connected to it (e.g., when itreceives the data message through the tunnel, it identifies that thenext N service machines in the service chain are connected to it when itreceives the data message).

When the service node receives the data message from a connected servicemachine and the service machine for the next service operation in theservice chain is not connected to the service node, the service noderesolves the next service machine's network address on the SFP list(stored in its connection storage for the data message) to an underlaytunnel that terminates at the service node connected to the next servicemachine. In some embodiments, the current service node identifies thenetwork address of the next service machine by using the service indexthat was embedded in the data message's tunnel header and is now storedin the connection storage of the current service node.

After resolving the next service machine's network address to anotherunderlay tunnel, the current service node sends a re-encapsulated datamessage along this underlay tunnel to the next service node. The tunnelheader of the re-encapsulated data message includes the SFP list thatwas contained in the original tunnel header that the current servicenode received. In some embodiments, the current service node modifiesthis SFP list to remove any network address of any service machine thatconnects to the current service node and that performed a serviceoperation in the service chain on the data message. In otherembodiments, the current service node does not remove the networkaddresses of any of its associated service machine that performed aservice operation on the data message, and instead simply adjusts theservice index in the tunnel header to identify the network address ofthe next service machine that has to perform the next service operationin the service chain.

To formulate the tunnel header for the re-encapsulated data message, thecurrent service node in some embodiments retrieves the informationstored from the received data message's tunnel header from itsconnection storage and updates this information (e.g., updates the SFPlist or adjusts the service index). In some embodiments, the servicenode decrements the service index as the service machine networkaddresses are identified in the embedded SFP list in reverse order, withthe first service machine's address appearing last in the list while thelast service machine's address appears first in the list.

In some cases, the last service node communicatively connects to thedestination machine of the data message (e.g., the last SVM and thedestination GVM execute on the same host computer) without having to gothrough intervening routing/switching fabric. In these embodiments, thelast service node supplies the decapsulated data message to thedestination machine. In other cases, the last service node has to gothrough intervening routing/switching fabric to reach the message'sdestination. In these cases, after receiving the processed data messagefrom the last service machine, the last service node forwards the datamessage through intervening routing fabric to its destination. In someof these embodiments, the last service node forwards this data messageto its destination through another tunnel.

Some embodiments use Generic Network Virtualization Encapsulation(Geneve) tunneling protocol to carry the service function pathinformation (e.g., the service index and the list of service machinenetwork addresses) and the tenant identifier. In some embodiments, theSFP information is embedded in a new Geneve service function list optionTLV (type, length, value) for use between service nodes (called networkvirtualization edges, NVEs) performing the service forwarding operationin the same network virtualization overlay over Layer 3 (NVO3) domain.

In addition to embedding the SFP information and the tenant identifierin the data message tunnel headers, the method of some embodiments alsocaptures and embeds contextual metadata in these tunnel headers, so thatsome or all of the service machines along the SFP can process to performtheir service operations. For instance, the method can embed the datamessages traffic type, and the service machine can based its serviceoperation on this traffic type (e.g., perform its load balancingoperation or firewall operation based on the traffic type). Otherexamples of the contextual metadata include generated QoS ratings, layer7 parameters, process identifiers, user identifiers, group identifiers,etc.

In addition to basing its service operation on metadata embedded in areceived data message's tunnel header, a service machine along the SFPin some embodiments can also generate metadata and provide the metadatato its associated service node to embed in the tunnel header that theservice node uses to re-encapsulate the data message before sending italong the SFP. For instance, the service machine might be a DPI machinethat identifies the traffic type and provides this traffic type to beembedded in the data message tunnel header for subsequent servicemachines to use in performing their operations. Alternatively, theservice machine might provide, or modify a provided, a QoS rating to beembedded in the data message tunnel header for subsequent servicemachines to use in performing their operations.

After receiving metadata from a service machine, the service-machine'sassociated service node in some embodiments might have to perform a newclassification operation to validate the remaining service operationsand/or remaining service machines in the SFP list or to re-specify theseremaining operations and/or service machines. In some embodiments, thisservice node cannot perform such a classification operation, and henceforwards the data message and the metadata (e.g., the tunnelencapsulated data message with the metadata) to another service node toperform this classification operation. After validating or re-specifyingthe remainder of the SFP list, the service node (either the oneassociated with the service machine or the other one that performs theclassification operation, if any) forwards the data message in a tunnelto the service node associated with the next service machine in this SFPlist.

The above-described methodology is used in some embodiments to expressservice chains in single tenant environments. Thus, one of ordinaryskill will realize that some embodiments of the invention are equallyapplicable to single tenant datacenters. Conversely, in someembodiments, the above-described methodology is used to carry servicechain specification across different datacenters of different datacenterproviders when one entity (e.g., one corporation) is a tenant inmultiple different datacenters of different providers. In theseembodiments, the tenant identifiers that are embedded in the tunnelheaders have to be unique across the datacenters, or have to betranslated when they traverse from one datacenter to the next.

The preceding Summary is intended to serve as a brief introduction tosome embodiments of the invention. It is not meant to be an introductionor overview of all inventive subject matter disclosed in this document.The Detailed Description that follows and the Drawings that are referredto in the Detailed Description will further describe the embodimentsdescribed in the Summary as well as other embodiments. Accordingly, tounderstand all the embodiments described by this document, a full reviewof the Summary, Detailed Description, the Drawings and the Claims isneeded. Moreover, the claimed subject matters are not to be limited bythe illustrative details in the Summary, Detailed Description and theDrawing.

BRIEF DESCRIPTION OF THE DRAWINGS

The novel features of the invention are set forth in the appendedclaims. However, for purposes of explanation, several embodiments of theinvention are set forth in the following figures.

FIG. 1 illustrates an example of specifying and using a serviceoperation chain according to some embodiments of the invention.

FIG. 2 illustrates a new Geneve tunnel header of some embodiments.

FIG. 3 illustrates a new Geneve base header of some embodiments.

FIG. 4 shows a new SFL (service function list) option TLV header of theGeneve tunnel header of some embodiments.

FIG. 5 illustrates an SFL flag field of the new SFL option TLV header ofsome embodiments.

FIG. 6 illustrates an HMAC (hashed message authentication code) sub-TLVof the new SFL option TLV of some embodiments.

FIG. 7 illustrates a new Geneve NSH (network service header) metadataoption TLV of some embodiments.

FIG. 8 conceptually illustrates a process performed by an ingressservice node in some embodiments.

FIG. 9 illustrates a process that a service node performs when itreceives a Geneve-encapsulated data message.

FIG. 10 illustrates a host computer that is used in some embodiments toexecute the virtual machines, service machines and service nodes of someembodiments.

FIG. 11 illustrates an example of how the service nodes are managed insome embodiments.

FIGS. 12 and 13 illustrate examples for forwarding and processingmetadata in connection with service operations that are performed byservice machines in some embodiments.

FIG. 14 conceptually illustrates a computer system with which someembodiments of the invention are implemented.

DETAILED DESCRIPTION

In the following detailed description of the invention, numerousdetails, examples, and embodiments of the invention are set forth anddescribed. However, it will be clear and apparent to one skilled in theart that the invention is not limited to the embodiments set forth andthat the invention may be practiced without some of the specific detailsand examples discussed.

For a multi-tenant environment, some embodiments of the inventionprovide a novel method for specifying a set of service operations that aset of service machines have to perform on a tenant's data message flow.In some embodiments, the service machines can be standalone serviceappliances or computers, and/or service machines (e.g., virtualmachines, containers, etc.) executing on host computers along with otherservice machines and/or tenant machines. Also, in some embodiments, oneor more of the service machines are middlebox service machines thatperform middlebox service operations, such as load balancing operations,firewall operations, intrusion detection operations, intrusionprevention operations, encryption/decryption operations, etc.

In some embodiments, the method performs a classification operation onthe tenant's data message flow in order to identify a sequence ofservice operations (also referred to below as a chain of serviceoperations) to perform on the data message flow. After identifying thissequence, the method in some embodiments embeds the identified sequencein tunnel headers that it uses to encapsulate the flow's data messages.The method in some embodiments identifies the service chain, and embedsthis chain in the tunnel headers, by identifying and embedding a set ofnetwork addresses (e.g., destination IP addresses) of a set of servicemachines that are to perform the service operations in the chain. Inthese tunnel headers, the method also embeds a tenant identifier (e.g.,embeds a VNI, virtual network identifier) to specify that the datamessages are associated with a particular tenant (e.g., are emanatingfrom a machine of the particular tenant). The method then sends theseencapsulated messages along a tunnel to a service machine that performsa first service operation in the identified service chain.

In some embodiments, the service machines addressed by the networkaddresses embedded in the tunnel communicatively connect to servicenodes that are connected to each other through a set of tunnels. Servicenodes can be different types of network elements in differentembodiments. For instance, in some embodiments, the service nodes can be(1) host computers on which the service machines execute, (2) standaloneforwarding elements connected to the service machines, or (3) serviceappliances that perform both the service node functionality (to connectto other service nodes via tunnels) and the service machinefunctionality (to perform one or more service operations). Also, in someembodiments, one service node can connect to two or more servicemachines in the identified service chain.

Accordingly, after identifying the service chain for a data message andencapsulating the data message with a tunnel header that contains thenetwork addresses of the service-machine set that perform the serviceoperations in the identified service chain, the method in theseembodiments forwards the encapsulated data message along a tunnel to aservice node that communicatively connects to the first service machinethat performs on the data message the first service operation in theidentified service chain. In some embodiments, the outer portion of thetunnel header of the encapsulated message identifies the network address(e.g., IP address) of the first service machine's service node (or avirtual tunnel endpoint (VTEP) of the first service machine's servicenode) as the destination network address (e.g., destination IP address)of the encapsulated data message.

As used in this document, data messages refer to a collection of bits ina particular format sent across a network. One of ordinary skill in theart will recognize that the term data message is used in this documentto refer to various formatted collections of bits that may be sentacross a network, such as Ethernet frames, IP packets, TCP segments, UDPdatagrams, etc. Also, as used in this document, references to L2, L3,L4, and L7 layers (or layer 2, layer 3, layer 4, layer 7) are referencesrespectively to the second data link layer, the third network layer, thefourth transport layer, and the seventh application layer of the OSI(Open System Interconnection) layer model.

FIG. 1 illustrates an example of specifying and using a serviceoperation chain according to some embodiments of the invention. In thisexample, five service machines 130-138 perform five service operationson a data message 100 sent from one guest virtual machine (GVM) 102executing on one host 104 in a multi-tenant datacenter to another GVM106 executing on another host 108 in the same datacenter. The GVMsbelong to a tenant that is associated in the datacenter with aparticular virtual network identifier VNI.

Four of these service machines 130-136 are service virtual machines(SVMs) executing on three hosts 112-116 in the datacenter, with two ofthese SVMs 132 and 134 executing on one host 114. The fifth servicemachine is a service appliance 138. All of these service machines130-138 perform middlebox service operations. In the example illustratedin FIG. 1, the data message 100 is encapsulated with tunnel headers140-146 and forwarded to the service machines 130-138 by service nodes120-126 and 138 that are connected to each other through tunnels150-156. The service appliance 138 acts as its own service node.

Like most tunnel headers, each of the tunnel headers 140-146 has anouter portion (not shown) that identifies the IP addresses of the sourceand destination endpoints of the tunnel as the source and destination IPaddresses of the data message 100 encapsulated by the tunnel header. Insome embodiments, the source and destination tunnel endpoints are VTEPsassociated with the two service-node endpoints of the tunnel. Forexample, the outer portion of the tunnel header 140 identifies the IPaddresses of a VTEP of the ingress service node 120 as the encapsulateddata message's source IP address, while identifying the IP addresses ofa VTEP of the service node 122 as the encapsulated data message'sdestination IP address.

Each of the tunnel headers 140-146 includes the tenant's VNI and aservice function path (SFP) list that identifies the remaining portionof the service chain at each service node along the service path. Asshown, the SFP list in some embodiments is expressed in terms of the IPaddresses of the service machines 130-138. The SFP list along with theservice nodes (connected to the service machines on the SFP) and thetunnels that connect these service nodes define a service function chain(SFC) for the data message flow.

In FIG. 1, the service node 120 is an ingress service node that receivesthe data message from the source GVM 102. As further described below,this service node in some embodiments is formed by a software forwardingelement (SFE) and a service orchestrator that execute on the source hostcomputer 104. The SFE intercepts the data message sent by the source GVM102 and forwards it to the service orchestrator, which then performs aclassification operation on the data message, in order to identify a setof service operations to perform on the data message flow.

For some data message flows, the classification operation selects theidentified set of service operations from several candidate sets ofservice operations that are viable service operation sets for similardata message flows of the tenant. In some embodiments, theclassification operation is based on a set of attributes associated withthe data message flow. This attribute set in some embodiments justincludes the data message flow's layer 2-4 header values. In otherembodiments, however, the attribute set includes contextual attributesrelated to the data message flow, such as the data message flow'straffic type (i.e., the type of content carried in the data messageflow), QoS ratings, layer 7 parameters, process identifiers, useridentifiers, group identifiers, etc.

After identifying the service chain for the intercepted data message,the ingress service node 120 in some embodiments embeds the identifiedservice chain in the tunnel header 140 that it uses to encapsulate thedata message 100. As shown, the service node in some embodimentsidentifies and embeds the service chain in terms of the IP addresses ofthe service machines 130-138 that are to perform the service operationsin the chain. In addition to the IP addresses of these service machines,the ingress service node 120 embeds in the tunnel header a tenantidentifier (which in this case is the particular tenant's VNI) tospecify that the data message 100 is associated with the particulartenant (e.g., are emanating from a GVM of the particular tenant).

The ingress service node 120 in some embodiments embeds other attributes(e.g., other network addresses) in the tunnel header 140. Also, in someembodiments, the ingress service node 120 embeds in the tunnel header140 a service operation descriptor (e.g., tag) for each service machinein order to explain the type of service operation that the servicemachine performs. In other embodiments, no such descriptor is embeddedin the tunnel header. Also, the ingress service node 120 in someembodiments embeds a service index value in the tunnel header thatidentifies one of the embedded network addresses as the network addressof the “current” service operation. As further described below,subsequent service nodes use this index in some embodiments to identifythe next service machine for performing the next service operation in aservice chain.

After identifying the service chain for the data message 100 andencapsulating the data message with the tunnel header 140, the ingressservice node 120 passes the encapsulated data message along the tunnel150 to the service node 122 that communicatively connects to the firstservice machine 130 that performs on the data message the first serviceoperation in the identified service chain. As mentioned above, the outerportion of the tunnel header 140 in some embodiments identifies the IPaddresses of a VTEP of the ingress service node 120 as the encapsulateddata message's source IP address, while identifying the IP addresses ofa VTEP of the service node 122 as the encapsulated data message'sdestination IP address.

At each service node 122-126 along the SFP, including the service node138, the service node inspects the tunnel header and determines that thereceived data message is addressed to a service machine communicativelyconnected to the service node. The service node makes this determinationin some embodiments by extracting the service index from the tunnel,using this index to retrieve the network address of the current servicemachine that has to perform the service operation, and then determiningthat this service machine is one that is connected to the service node.

Once a service node determines that the received data message isaddressed to one of its associated service machines, the service noderemoves the tunnel header (i.e., decapsulates the received datamessage), stores information (e.g., the SFP and service index) from thisheader in a connection storage for later reuse, and provides the datamessage to the identified, connected service machine for processing. Asfurther described below, the stored information in some embodimentsincludes information for the service node to re-assemble the tunnelheader if it needs to re-encapsulate the data message after it has beenprocessed by the service machines, in order to forward the data messageto another service node.

Once the service machine performs its service operation on the datamessage, it returns the data message to the service node. In some case,a service machine might instruct the service node to drop the datamessage based on its service operation. In some embodiments, a servicenode (like service node 124) can be connected to two or more servicemachines (e.g., service machines 132 and 134) that perform two or moresuccessive service operations in a service chain. In such a case, theservice node (e.g., node 124) provides the data message (in its currentdecapsulated state) to the next service machine (e.g., the servicemachine 134) in the service chain, after receiving the data message froma prior service machine (e.g., the service machine 132) in the chain(assuming that the prior service chain did not drop, or instruct theservice node, to drop the data message). In some embodiments, theservice node determines that the next service machine is also connectedto it after receiving the data message from the prior service machineconnected to it. In other embodiments, the service node makes thisdetermination before passing the data message to any service machineconnected to it (e.g., when it receives the data message through thetunnel, it identifies that the next N service machines in the servicechain are connected to it when it receives the data message).

When the service node receives the data message from a connected servicemachine and the service machine for the next service operation in theservice chain is not connected to the service node, the service noderesolves the next service machine's network address on the SFP list(stored in its connection storage for the data message) to an underlaytunnel that terminates at the service node connected to the next servicemachine. In some embodiments, the current service node identifies thenetwork address of the next service machine by using the service indexthat was embedded in the data message's tunnel header and is now storedin the connection storage of the current service node.

After resolving the next service machine's network address to anotherunderlay tunnel, the current service node sends a re-encapsulated datamessages along this underlay tunnel to the next service node. Again, theouter portion of the tunnel header identifies the IP addresses of thesource and destination service nodes of the tunnel as the source anddestination IP addresses of the encapsulated data message. This tunnelheader also includes the SFP that was contained in the original tunnelheader that the current service node received minus any network addressof any service machine that connects to the current service node andthat performed a service operation in the service chain on the datamessage. Thus, the SFP list 162 that the service node 122 inserts in thetunnel header 142 does not include the IP address of service machine130. Similarly, the SFP list 164 that the service node 124 inserts inthe tunnel header 144 does not include the IP addresses of prior servicemachines 130, 132, and 134, while the SFP list 166 that the service node138 inserts in the tunnel header 146 does not include the IP address ofservice machine machines 130, 132, 134 and 138.

In other embodiments, the service nodes do not remove the networkaddresses of their associated service machines before sending out there-encapsulated data message. As further described below, a currentservice node in these embodiments simply adjusts the service index inthe tunnel header to identify the network address of the next servicemachine that has to perform the next service operation in the servicechain. To formulate the tunnel header for the re-encapsulated datamessage, the current service node in some embodiments retrieves theinformation stored from the received data message's tunnel header fromits connection storage and updates this information (e.g., updates theSFP list or adjusts the service index). In some embodiments, the servicenode decrements the service index as the service machine networkaddresses are identified in the embedded SFP list in reverse order, withthe first service machine's address appearing last in the list while thelast service machine's address appears first in the list.

In some cases, the last service node communicatively connects to thedestination machine of the data message (e.g., the last SVM and thedestination GVM execute on the same host computer) without having to gothrough intervening routing/switching fabric. In these embodiments, thelast service node supplies the decapsulated data message to thedestination machine. In other cases, the last service node has to gothrough intervening routing/switching fabric to reach the message'sdestination. This is the case in FIG. 1. After receiving the processeddata message 100 from the last service machine 136, the service nodeforwards the data message along tunnel 158 through intervening routingfabric to its destination. To send this data message along this tunnel,the service node encapsulates the data message with a tunnel header 148that includes the tenant's VNI but not an SFP list as all the serviceoperations have been performed on the data message.

Some embodiments use Generic Network Virtualization Encapsulation(Geneve) tunneling protocol to carry the service function pathinformation (e.g., the service index and the list of service machinenetwork addresses) and the tenant identifier.

In some embodiments, the SFP information is embedded in a new Geneveservice function list option TLV (type, length, value) for use betweenservice nodes (called network virtualization edges, NVEs) performing theservice forwarding operation in the same network virtualization overlayover Layer 3 (NVO3) domain.

In addition to embedding the SFP information and the tenant identifierin the data message tunnel headers, the service nodes of someembodiments also capture and embed contextual metadata in these tunnelheaders, so that some or all of the service machines along the SFP canprocess to perform their service operations. For instance, the servicenodes can embed the data message's traffic type, and the service machinecan base its service operation on this traffic type (e.g., perform itsload balancing operation or firewall operation based on the traffictype). Other examples of the contextual metadata include generated QoSratings, layer 7 parameters, process identifiers, user identifiers,group identifiers, etc.

In addition to basing its service operation on metadata embedded in areceived data message's tunnel header, a service machine along the SFPin some embodiments can also generate metadata and provide the metadatato its associated service node to embed in the tunnel header that theservice node uses to re-encapsulate the data message before sending italong the SFP. For instance, the service machine might be a DPI machinethat identifies the traffic type and provides this traffic type to beembedded in the data message tunnel header for subsequent servicemachines to use in performing their operations. Alternatively, theservice machine might provide, or modify a provided, a QoS rating to beembedded in the data message tunnel header for subsequent servicemachines to use in performing their operations.

In some embodiments, the metadata returned by the service machine to theservice node includes an SFP list identifier that the service node usesto identify the SFP list associated with the processed data message. Insome of these embodiments, the service machine has this SFP listidentifier because when the service node provides the data message tothe service machine, it provides the SFP list identifier to the servicemachine as well.

After receiving metadata from a service machine, the service-machine'sassociated service node in some embodiments might have to perform a newclassification operation to validate the remaining service operationsand/or remaining service machines in the SFP list or to re-specify theseremaining operations and/or service machines. In some embodiments, thisservice node cannot perform such a classification operation, and henceforwards the data message and the metadata (e.g., the tunnelencapsulated data message with the metadata) to another service node toperform this classification operation. After validating or re-specifyingthe remainder of the SFP list, the service node (either the oneassociated with the service machine or the other one that performs theclassification operation, if any) forwards the data message in a tunnelto the service node associated with the next service machine in this SFPlist.

FIG. 2 illustrates the Geneve tunnel header 200 of some embodiments. Asshown, this tunnel header includes an outer header 205, a protocol field210, a Geneve base header 215, an SFL (service function list) option TLV220, and a metadata option TLV 225. As described above, the outer header205 includes the network addresses (e.g., source and destination IPaddresses of the two tunnel endpoints, with the source and destinationdesignation depending on the direction of the message flow) in theunderlay network that allow the encapsulated data message to traversethe underlay network and reach the tunnel destination endpoint. Theprotocol field 210 specifies a UDP protocol as well as attributesassociated with this protocol.

As further described by reference to FIG. 3, the Geneve base header 215is 64-bit wide and stores several tunnel parameters, including thetenant identifier and the option length. The Geneve base header isfollowed by zero or more options in TLV format. In the exampleillustrated in FIG. 2, the options include a new SFL option TLV and anew metadata option TLV. As further described below by reference to FIG.4, the SFL option TLV includes the SFP list and the service index. Themetadata option TLV stores metadata associated with the data message inthe NSH metadata format. This metadata option TLV is described below byreference to FIG. 7. Other embodiments do not use this metadata optionTLV, and instead pass metadata relating to the data message in an L2VLAN header or a Q-in-Q header, or another encapsulation that is knownby both the service nodes and service machines.

FIG. 3 illustrates the Geneve base header 215 of some embodiments. Asshown, this header in some embodiments is 64-bit wide and stores severaltunnel parameters. Its version field 305 is a 2-bit value that specifiesthe current Geneve tunnel version being used. Tunnel endpoints thatreceive messages with unknown versions drop the messages.Non-terminating devices processing Geneve packets with an unknownversion number treat them as UDP packets with an unknown payload.

The option length field 310 specifies the length of the options fields,expressed in four byte multiples, not including the eight byte fixedtunnel header. This results in a minimum total Geneve header size of 8bytes and a maximum of 260 bytes. The start of the payload headers canbe found using this offset from the end of the base Geneve header.

The O bit 315 specifies whether the data message is an OAM frame thatcontains a control message instead of a data payload. Endpoints do notforward the payload of this message and transit devices do not attemptto interpret or process it. Since control messages are not frequent, theendpoints typically direct these messages to a high priority controlqueue. The transit devices do not alter forwarding behavior on the basisof this bit, such as ECMP link selection.

The C bit 320 is a critical option field that when set, indicates thatthe options are present. One or more options have the critical bit set.If this bit is set then tunnel endpoints parses the options list tointerpret any critical options. When this bit is set, endpoints mustdrop the encapsulated message if they do not recognize this option. Ondevices where option parsing is not supported, the frame is dropped onthe basis of the “C” bit in the base header. If the bit is not set,tunnel endpoints may strip all options using “Opt Len” and forward thedecapsulated frame. Transit devices do not drop or modify packets on thebasis of this bit.

The first set of reserved bits 325 are 6 bits that must be zero ontransmission and ignored on receipt. The protocol type bits 330 are 16bits that express the type of the protocol data unit appearing after theGeneve header. The VNI bits 335 express a 24-bit identifier for a uniqueelement of a virtual network. In many situations, this may represent anL2 segment; however, the control plane defines the forwarding semanticsof decapsulated packets. The VNI may be used as part of ECMP forwardingdecisions or may be used as a mechanism to distinguish betweenoverlapping address spaces contained in the encapsulated packet whenload balancing across CPUs. The second set of reserved bits are 8 bitsand must be zero on transmission and ignored on receipt.

The Geneve base header is followed by zero or more options in TLVformat. Each option includes a four-byte option header and a variableamount of option data interpreted according to the option type. FIG. 4shows the SFL option TLV header 220 of some embodiments. The SFL optionTLV is 8 bytes in this example. This option TLV 220 contains theparameters needed to specify the SFP list and service index. As shown,the option header 405 includes a 16-bit option class, which is thenamespace for a type field 410 that indicates the format of the datacontained in this option. The type field is to be assigned by IANA, whenit creates a “Geneve Option Class” registry to allocate identifiers fororganizations, technologies, and vendors that have an interest increating types for options.

The three R bits 415 are option control flags reserved for future use.These must be zero on transmission and ignored on receipt. The lengthfield includes 5 bits. Length of the option, expressed in four bytemultiples excluding the option header. The total length of each optionmay be between 4 and 128 bytes ([1 to 32]*4). In some embodiments, adata message in which the total length of all options is not equal tothe option length in the base header is invalid and is dropped ifreceived by an endpoint.

As shown, the variable option portion 475 of the SFL option TLV header220 includes the four-byte header field 425, an SFP list 450 and anoptional sub-type TLV 455. The SFP list provides 32 or 128 bit addressesof the service machines in the service chain embedded in the Genevetunnel header. The header field 425 includes a version field 430, SFLflag field 435, reserved bits 440, and SFP index field 445.

The version field 430 is a 5-bit value that specifies the current SFLoption TLV version being used. Tunnel endpoints that receive messageswith unknown versions drop the messages. The reserved bits 400 shouldnot be set on transmission and are to be ignored on receipt. The SFPIndex contains the service index in SFP List. In some embodiments, aservice node decrements the service index after the data message hasbeen processed by one of the node's service machines. This is becausethe SFP List is encoded starting from the last hop of the path, i.e.,the first element of the list (SF List [0]) contains the last servicefunction of the path while the last element of the SF List (SF List[n])contains the first service function in the path.

The SFL flag field is an eight-bit field 435 that is illustrated in FIG.5. The first value 505 in this field is an HMAC flag, while the othervalues 510 are left unused. When set, the first value 505 specifies thatthe HMAC (hashed message authentication code) sub-TLV is present and isencoded as the last sub-TLV 455. HMAC sub-TLV carries parameters for acryptographic hash function and a secret cryptographic key. In someembodiments, the HMAC is used to simultaneously verify both the dataintegrity and the authentication of a message.

In some embodiments, only the service nodes that are the destinations ofthe Geneve tunnel packet will be inspecting the SFP list defined in theSFL Option TLV of the tunnel header. In one deployment that uses theGeneve SFL Option TLVs, only service nodes within a single NVO3administrative domain are trusted nodes that are enabled to review theseTLVs. Service nodes ignore the Geneve SFL lists created by outsidersbased on information from the network virtualization authority or someother trusted control plane information.

To prevent non-participating service node from using the Geneve SFLoption TLV, some embodiments use an optional security sub-TLV in the SFLoption TLV that is based on a key-hashed message authentication code(HMAC). The HMAC optional sub-TLV is located at the end of the GeneveService Function List option TLV. The purpose of the HMAC optionalsub-TLV is to verify the validity, the integrity, and the authorizationof the Geneve SFL option TLV itself.

The HMAC sub-TLV will contain (1) HMAC Key-ID, 32 bits wide, and (2) anHMAC field, which is 256 bits wide. The HMAC field is the output of theHMAC computation using a pre-shared key identified by HMAC Key-ID and ofthe text that is formed by concatenating (1) the source IPv4/IPv6 Genevetunnel address, (2) the version and flags data, (3) HMAC Key-ID, and (4)all addresses in the SFP list. The HMAC Key-ID field serves as an indexto the right combination of pre-shared key and hash algorithms andexpect that a value of 0 means that there is no HMAC field. The HMACselection of a hash algorithm and pre-shared key management in someembodiments follow the procedures described inDraft-ietf-6man-segment-routing-header.

FIG. 6 illustrates the HMAC sub-TLV 455 for some embodiments of theinvention. This sub-TLV contains the HMAC information. The type field605 is to be assigned by IANA. The length field 610 is eight bits toexpress 38 octets of HMAC information. The reserved bits 615 is 2 octetswide. These bits should not be set on transmission and should be ignoredon receipt. The HMAC Key ID 620 is 4 octets wide, while the HMACparameter field 625 is 32 octets wide. When the HMAC sub-TLV is present,the H-Flag is set, and the HMAC sub-TLV is encoded as the last sub-TLV.When the H-flag is set, the service node inspecting the Geneve SFP listOption TLV has to find the HMAC sub-TLV in the last 38 octets of theoption TLV.

FIG. 7 illustrates a new Geneve NSH metadata option TLV 225 of someembodiments. As shown, this TLV 225 has a 32-bit header, which includethe same first 32 bits of the option, type, reserved and length fields405, 410, 415, and 420 as the first 32 bits of the SFL Option TLV 220 ofFIG. 4. The type field 410 in the NSH metadata option TLV headerspecifies one of two metadata types, MD type 1 or MD type 2, of the NSHmetadata format. As shown in FIG. 7, the TLV 225 also include fixed- orvariable-sized option data 725. As shown, the option data is eitherfixed 16 bytes of value for MD-Type 1 metadata, or variable sized forMD-Type 2 metadata.

FIG. 8 conceptually illustrates a process 800 performed by an ingressservice node (like node 120) of some embodiments. This processidentifies an SFP list for a data message and embeds this SFP list in aGeneve tunnel header that it uses to encapsulate the data message beforesending this encapsulated message along a tunnel to the service nodethat is communicatively connected to the first service machine. In someembodiments, the ingress service node is formed by an SFE (e.g.,software switch) and a service orchestrator that execute on the sourcehost computer (e.g., computer 104) along with one or more GVMs (e.g.,GVM 102). The GVMs in some embodiments communicatively connect with theSFE, which forwards data messages to and from the GVMs.

As shown, the process 800 initially receives a data message from atenant GVM (e.g., GVM 102) executing on its host (e.g., 104). In someembodiments, the process 800 receives this data message when the SFEintercepts and forwards it to the service orchestrator. Next, based on aset of attributes associated with the data message, the process (e.g.,the service orchestrator) performs (at 810) a classification operationon the data message, in order to identify a set of service operations toperform on the data message flow.

For some data message flows, the classification operation selects theidentified set of service operations from several candidate sets ofservice operations that are viable service operation sets for similardata message flows of the tenant. Also, the classification operation isbased on different sets of data-message flow attributes in differentembodiments. In some embodiments, this set just includes the datamessage flow's layer 2-4 header values, while in other embodiments, theattribute set includes contextual attributes related to the data messageflow, such as the data message flow's traffic type (i.e., the type ofcontent carried in the data message flow), QoS ratings, layer 7parameters, process identifiers, user identifiers, group identifiers,etc.

For instance, in some embodiments, the process performs thisclassification operation by comparing one or more attributes of the datamessage (e.g., the data message's 5-tuple identifier and/or associatedmetadata) with rule identifiers of several service rules stored in arule storage. In addition to its rule identifier, each rule specifies aset of service actions, which in some embodiments are specified as IPaddresses of service machines for performing the service actions. Asmentioned above, each IP address in some embodiments can be specified asa VIP that specifies a service cluster of two or more service machinesthat performs the same service operation. The service node in someembodiments performs a load balancing operation to convert each servicemachine cluster's VIP to one DIP for the flow of the data message beingprocessed. A host architecture for capturing and using contextualattributes will be further described below by reference to FIG. 10.

After identifying (at 810) the service chain for the intercepted datamessage, the process 800 embeds (at 815) the identified service chain inan SFL option TLV 220 of a Geneve tunnel header 200 that it will use toencapsulate the received data message. As described above, the SFLoption TLV stores the service chain in terms of the IP addresses of theservice machines that are to perform the service operations in thechain. Also, as further described above, the SFL option TLV stores theseIP addresses in reverse order, with the first service machine's addressappearing last in the list while the last service machine's addressappears first in the list.

In the SFL option TLV, the process also stores (at 815) the serviceindex value 445. The process sets this value to identify the lastnetwork address in the SFP list, which is the address of the firstservice machine. The service index value is used to identify theembedded network address of the “current” service operation, andsubsequent service nodes use this index in some embodiments to identifythe next service machine for performing the next service operation in aservice chain. In some embodiments, the process 800 embeds in the SFLoption TLV a service operation descriptor (e.g., tag) with each servicemachine address to explain the type of service operation that theservice machine performs. In other embodiments, no such descriptor isembedded in the tunnel header. If the Geneve tunnel needs to have itsHMAC parameters set, the process also defines (at 815) the HMAC sub-TLVand sets its parameters.

At 815, the process 800 also embeds in the base header 215 of the Genevetunnel header the VNI of the tenant associated with the source GVM thatsent the received data message. After embedding the VNI, the process 800identifies (at 820) one or more metadata attributes associated with thereceived data message, and stores the identified metadata in an NSHmetadata option TLV 225. In different embodiments, the process 800identifies and embeds different metadata. Examples of such metadatainclude the data messages traffic type, a QoS ratings, layer 7parameters, process identifiers, user identifiers, group identifiers,etc. A host architecture for capturing and embedding metadata attributeswill be further described below by reference to FIG. 10.

The process embeds this metadata in the Geneve tunnel header because oneor more services along the SFP can process the metadata in order toperform their service operations. In some cases, the service machinesalong the identified SFP do not use any metadata associated with thedata message to perform their operations on the data message. In thesecases, the process does not embed any metadata in the Geneve tunnelheader and therefore does not include the NSH metadata option TLV inthis header.

Next, at 825, the process configures other parts of the Geneve tunnelheader. For instance, the process stores in the outer portion header 205of the tunnel header 200 the L2 and L3 network addresses of its VTEP(e.g., a VTEP associated with its SFE) and the VTEP of the service nodeassociated with the first service machine as the source and destinationnetwork addresses. At 825, the process defines the UDP protocol in theGeneve tunnel header, and sets any other fields that need to be define,per the discussion above and the tunnel deployment configuration beingused.

After finalizing the tunnel header configuration (at 825), the processpasses (at 830) the encapsulated data message along a Geneve tunnel tothe service node (e.g., node 122) associated with the first servicemachine (e.g., service machine 130) that performs on the data messagethe first service operation in the identified service chain. To sendthis data message, the process in some embodiments resolves the IPaddress of the first service machine to the tunnel that connects theingress service node to the service node of the first service machine.After 825, the process ends.

In some cases, the ingress service node executes on a host computer thatexecutes the source machine (e.g., source VM or container) for a datamessage as well as the first service machine or the first severalservice machines that are to perform the first or first several serviceoperations on the data message. In these cases, the ingress service nodefirst passes the data message to this service machine or these servicemachines, before encapsulating the data message with a tunnel header andforwarding it to the next service machine in the chain.

FIG. 9 illustrates a process 900 that a service node performs when itreceives a Geneve-encapsulated data message. In some embodiments, thisservice node executes on a host computer along with one or more servicemachines (e.g., SVMs or service containers) and one or more tenantmachines (e.g., GVMs). As shown, the process inspects (at 905) thetunnel header and determines that the received data message is addressedto a service machine communicatively connected to the service node. Theservice node makes this determination in some embodiments by extractingthe service index from the tunnel, using this index to retrieve thenetwork address of the current service machine that has to perform theservice operation, and then determining that this service machine is onethat is connected to the service node.

Once the process 900 determines (at 905) that the received data messageis addressed to one of its associated service machines, the process 900(at 910) removes the tunnel header (i.e., decapsulates the received datamessage), and stores information (e.g., the SFP, service index,metadata, etc.) from this header in a connection storage for laterreuse. At 915, the process 900 in some embodiments provides the datamessage to the identified, connected service machine for processing andremoves the IP address of this service machine from the received SFPlist. Instead of removing the IP address of this service machine, theprocess 900 in other embodiments adjusts the current service index(e.g., decrements the service index by 1 in the embodiments that definethe IP addresses of the service machines in the reverse order) afterproviding the data message to the identified connected service machinefor processing.

When the extracted tunnel header contains metadata for the data message,and the service machine needs some or all of the metadata to perform itsservice operation, the process provides (at 915) the needed metadata tothe service machine. In some embodiments, the process provides the datamessage and/or the metadata by passing one or more identifiers to theservice machine that identify the location at which the data messageand/or the metadata are stored in a memory.

Once the service machine performs its service operation on the datamessage, the process receives (at 920) the processed data message at theservice node. In some embodiments, the service machine returns metadataalong with the processed data message. In some embodiments, the servicemachine provides the data message and/or the metadata by passing one ormore identifiers to the process 900 that identify the location at whichthe processed data message and/or the metadata are stored in a memory.The returned metadata can be metadata that the service machine generatesin processing the data message or the data message's flow, or captures(e.g., through deep packet inspection) from the received data message orfrom the data message's flow.

In some embodiments, the metadata returned (at 920) by the servicemachine to the service node includes an SFP list identifier that theservice node uses to identify the SFP list associated with the processeddata message. In some of these embodiments, the service machine has thisSFP list identifier because when the service node provided (at 915) thedata message to the service machine, it provided the SFP list identifierto the service machine as well.

To capture or generate the metadata, the service machine in someembodiments might need to process several data messages that are part ofthe same data message flow as the data message for which the process 900is performed. For instance, the service machine might have to perform asoft connection termination to examine the content of the data messagesin the flow. Hence, in these embodiments, the service node might providemultiple data messages that are part of the same flow before it receivesprocessed results for earlier supplied data messages.

In some cases, a service machine might instruct the service node to dropthe data message based on its service operation. Assuming that theservice machine does not direct the service node to drop the receiveddata message, the process 900 determines (at 925) whether it shouldperform classification operation to identify a new service chain for thedata message based on metadata returned (at 920) by the service machine.This operation is performed because the service machine in someembodiments can return metadata, which provides additional informationabout the data message being processed, and this additional informationmight require the service chain to be redefined for the data message.

In some embodiments, the determination (at 925) is based on whether theservice machine returned a certain type of metadata when it returned theprocessed data message. When the process determines (at 925) that it hasto perform a classification operation, it performs (at 930) theclassification operation to identify a new SFP list. In someembodiments, the process performs this classification operation bycomparing one or more attributes of the data message (e.g., the datamessage's 5-tuple identifier and associated metadata) with ruleidentifiers of several service rules stored in a rule storage. Inaddition to its rule identifier, each rule specifies a set of serviceactions, which in some embodiments are specified as IP addresses ofservice machines for performing the service actions. As mentioned above,each IP address in some embodiments can be specified as a VIP thatspecifies a service cluster of two or more service machines thatperforms the same service operation. The service node in someembodiments performs a load balancing operation to convert each servicemachine cluster's VIP to one DIP for the flow of the data message beingprocessed.

At 930, the process defines a Geneve tunnel header for the data message,and embeds the SFP list that it generated (at 930) in this tunnel headeralong with the source tenant machine's VNI, the service index for theSFP list, any needed metadata associated with the data message (possibleincluding metadata returned by the service machine at 920), and otherGeneve tunnel attributes. Next, at 935, the process encapsulates theprocessed data message with the tunnel header defined at 930, and sendsthe encapsulated data message along a Geneve tunnel to the next servicenode associated with the first service machine in the re-specified SFPlist. To send this data message, the process in some embodimentsresolves the IP address of the first service machine to the tunnel thatconnects the current service node to the service node of the firstservice machine. The outer portion of the tunnel header identifies thesource and destination IP addresses as the IP addresses of the VTEPs ofthe current service node and the next service node. After 935, theprocess 900 ends.

When the process determines (at 925) that it does not need to perform aclassification operation, the process determines (at 940) whether theSFP list for the data message is now empty. An empty SFP list would beindicate that all the service operations have been specified for thereceived data message. As mentioned above, the process 900 in someembodiments (at 915) removes the IP address of the last service machinefrom the SFP list or adjusts the service index, before supplying (at915) the data message to this service machine. In the embodiments thatdo not remove the service machine IP address from the SFP list andinstead adjust the service index value, the process makes thisdetermination (at 940) by determining whether the service index valueindicates that all of the service machines identified in the SFP listhave processed the data message. For instance, in some embodiments thatdecrement the service index each time the data message is passed toanother service machine, the process determines that the SFP list isempty when the service index reaches zero, or some other service indexvalue associated an empty SFP list.

When the process determines (at 940) that the SFP list is empty, theprocess determines (at 945) whether the destination of the data messageis on the same host computer (i.e., determines whether a machine withnetwork addresses (e.g., L2-L4 addresses) specified in the datamessage's header is executing on the same host computer). When thedestination is on the same host computer, the process passes (at 950)the processed data message to the destination machine, and then ends.When the destination is not on the same host computer, the process (at955) uses the destination IP address to identify the tunnel to use toforward the data message to its destination, and then encapsulates thedata message with a header of this tunnel before sending the datamessage along the tunnel to its destination (e.g., using tunnel 158 tosend the message 100 to SFE 128 of host 108 to pass the data message tothe GVM 106). The outer portion of the tunnel header identifies thesource and destination IP addresses as the IP addresses of the VTEPs ofthe current service node and the destination machine (when a standalonemachine) or a host computer on which the destination machine executes.After 955, the process ends.

When the process determines (at 940) that the SFP list is not empty(i.e., determines that this list or the service index still identifiesat least one IP address of at least one other service machine that hasto perform at least one other service operation), the process determines(at 960) whether the service machine associated with the next IP addressexecutes on the same host computer. In some embodiments, the processidentifies the network address of the next service machine by using theservice index that was embedded in the data message's tunnel header andis now stored in the connection storage of the current service nodeafter it was decremented at 915.

The process 900 performs the check at 950 because in some embodiments, aservice node (like service node 124) can be connected to two or moreservice machines (e.g., service machines 132 and 134) that perform twoor more successive service operations in a service chain. In such acase, the process returns to 915 (e.g., the service node 124) to providethe data message (in its current decapsulated state) to the next servicemachine (e.g., the service machine 134) in the service chain, afterreceiving the data message from a prior service machine (e.g., theservice machine 132) in the chain (assuming that the prior service chaindid not drop, or did not instruct the service node to drop, the datamessage). In some embodiments, the process determines (at 960) that thenext service machine is connected to it after receiving the data messagefrom the prior service machine connected to it. In other embodiments,the process makes this determination (at 905) before passing the datamessage to any service machine connected to it (e.g., when it receivesthe data message through the tunnel, it identifies that the next Nservice machines in the service chain are connected to it when itreceives the data message).

When the process determines (at 960) that the data message is not to benext processed by another service machine that executes on the same hostcomputer, the process resolves (965) the next service machine's networkaddress on the SFP list (stored in its connection storage for the datamessage) to the underlay tunnel that terminates at the service nodeconnected to the next service machine. After resolving the next servicemachine's network address to another underlay tunnel, the process sends(at 965) a re-encapsulated data message along this underlay tunnel tothe next service node. The outer portion of the tunnel header identifiesthe source and destination IP addresses as the IP addresses of the VTEPsof the current service node and the next service node.

This tunnel header also includes the SFP list that was contained in theoriginal tunnel header that the current service node with an adjustedservice index (e.g., with a decremented service index) or minus anynetwork address of any service machine associated with the currentservice node that performed a service operation in the service chain onthe data message (e.g., the SFP list 162 that the service node 122inserts in the tunnel header 142 does not include the IP address ofservice machine 130). To formulate the tunnel header (at 935 or 965) forthe re-encapsulated data message, the process 900 in some embodimentsretrieves the information stored from the received data message's tunnelheader from its connection storage and, if necessary, updates thisinformation (e.g., updates the metadata based on metadata received fromthe service machine(s)).

For some service operations (e.g., firewall operations, load balancingoperations) of some service machines, the service node stores theservice machine's operational result in a cache storage after processingthe first data message, so that the service node does not have tore-perform 900 for subsequent data messages that are part of the sameflow as the first data message. When the service node receives anotherdata message that is part of the same flow as the first data message,the process checks the cache storage to determine whether it hasprocessed an earlier data message of the same flow. If so, the servicenode retrieves the service machine's operational result for the earlierdata message from the cache storage, and uses this result for the datamessage that it is processing.

FIG. 10 illustrates a host computer 1000 that is used in someembodiments to execute the GVMs, service machines, and service nodes ofsome embodiments. This host computer performs context-rich,attribute-based services in a datacenter. This host computer 1000includes several GVMs 1005, SVMs 1032, a software forwarding element1010, a context engine 1050, service engines 1030, context-based servicerule storage 1040, context-attribute storage 1045, an attribute-mappingstorage 1023, a connection state cache storage 1025, a MUX (multiplexer)1027, and a context-engine policy storage 1043. The service engines 1030include a service orchestrator 1022, an encryption engine 1024, a loadbalancer 1026, a firewall engine 1028, and one or more other serviceengines (not shown).

In FIG. 10, the GVMs 1005 execute on a hypervisor. In some embodiments,the context engine 1050, the software forwarding element 1010, theservice engines 1030, the context-based service rule storages 1040, theconnection state cache storage 1025, the context-engine policy storage1043, and the MUX 1027 operate in the kernel space of the hypervisor,while the GVMs 1005 operate in the hypervisor's user space. In otherembodiments, one or more service engines are user space modules (e.g.,are service VMs).

In some embodiments, the GVMs 1005 serve as data end points in thedatacenter. Examples of such machines include webservers, applicationservers, database servers, etc. In some cases, all the VMs belong to oneentity, e.g., an enterprise that operates the host. In other cases, thehost 1000 operates in a multi-tenant environment (e.g., in amulti-tenant data center), and different GVMs 1005 may belong to onetenant or to multiple tenants.

Each GVM 1005 includes a GI agent 1048 that communicates with thecontext engine 1050 to provide context attribute sets to this engine,and to receive instructions and queries from this engine. Thiscommunication between the context engine 1050 and the GI agents 1048 isrelayed through the MUX 1027. One example of such a mux is the mux thatis used by the Endpoint Security (EPSec) platform of ESX hypervisors ofVMware, Inc. In some embodiments, the attributes collected by thecontext engine 1050 from the GI agents 1048 include a rich group ofparameters (e.g., layer 7 parameters, process identifiers, useridentifiers, group identifiers, etc.). U.S. patent application Ser. No.15/650,251 filed on Jul. 14, 2017, now published as U.S. PatentPublication 2018/0181423, further describes the capturing and use ofthese contextual attributes through the GI agent 1048. The U.S. patentapplication Ser. No. 15/650,251 is incorporated herein by reference.

The SVMs 132 perform service operations on data messages, includingthose forwarded by the service orchestrator 1022, as further describedbelow. As shown, each VM 1005 and 1032 includes a virtual networkinterface card (VNIC) 1055 in some embodiments. Each VNIC is responsiblefor exchanging messages between its VM and the SFE 1010. Each VNICconnects to a particular port 1060 of the SFE 1010. The SFE 1010 alsoconnects to a physical network interface card (NIC) (not shown) of thehost. In some embodiments, the VNICs are software abstractions createdby the hypervisor of one or more physical NICs (PNICs) of the host.

In some embodiments, the SFE 1010 maintains a single port 1060 for eachVNIC of each VM. The SFE 1010 connects to the host PNIC (through a NICdriver (not shown)) to send outgoing messages and to receive incomingmessages. In some embodiments, the SFE 1010 is defined to include a port1065 that connects to the PNIC's driver to send and receive messages toand from the PNIC. The SFE 1010 performs message-processing operationsto forward messages that it receives on one of its ports to another oneof its ports. For example, in some embodiments, the SFE tries to usedata in the message (e.g., data in the message header) to match amessage to flow-based rules, and upon finding a match, to perform theaction specified by the matching rule (e.g., to hand the message to oneof its ports 1060 or 1065, which directs the message to be supplied to adestination VM or to the PNIC).

In some embodiments, the SFE 1010 is a software switch, while in otherembodiments it is a software router or a combined softwareswitch/router. The SFE 1010 in some embodiments implements one or morelogical forwarding elements (e.g., logical switches or logical routers)with SFE executing on other hosts in a multi-host environment. A logicalforwarding element in some embodiments can span multiple hosts toconnect VMs that execute on different hosts but belong to one logicalnetwork.

Different logical forwarding elements can be defined to specifydifferent logical networks for different users, and each logicalforwarding element can be defined by multiple software forwardingelements on multiple hosts. Each logical forwarding element isolates thetraffic of the VMs of one logical network from the VMs of anotherlogical network that is serviced by another logical forwarding element.A logical forwarding element can connect VMs executing on the same hostand/or different hosts. In some embodiments, the SFE extracts from adata message a logical network identifier (e.g., a VNI) and a MACaddress. The SFE in these embodiments uses the extracted VNI to identifya logical port group, and then uses the MAC address to identify a portwithin the port group.

Software switches (e.g., software switches of hypervisors) are sometimesreferred to as virtual switches because they operate in software andthey provide the VMs with shared access to the PNIC(s) of the host.However, in this document, software switches are referred to as physicalswitches because they are items in the physical world. This terminologyalso differentiates software switches from logical switches, which areabstractions of the types of connections that are provided by thesoftware switches. There are various mechanisms for creating logicalswitches from software switches. VXLAN provides one manner for creatingsuch logical switches. The VXLAN standard is described in Mahalingam,Mallik; Dutt, Dinesh G.; et al. (2013 May 8), VXLAN: A Framework forOverlaying Virtualized Layer 10 Networks over Layer 3 Networks, IETF.

The ports of the SFE 1010 in some embodiments include one or morefunction calls to one or more modules that implement specialinput/output (I/O) operations on incoming and outgoing messages that arereceived at the ports. Examples of I/O operations that are implementedby the ports 1060 include ARP broadcast suppression operations and DHCPbroadcast suppression operations, as described in U.S. Pat. No.9,548,965. Other I/O operations (such as firewall operations,load-balancing operations, network address translation operations, etc.)can be so implemented in some embodiments of the invention. Byimplementing a stack of such function calls, the ports can implement achain of I/O operations on incoming and/or outgoing messages in someembodiments. Also, in some embodiments, other modules in the data path(such as the VNICs 1055, port 1065, etc.) implement the I/O functioncall operations instead of, or in conjunction with, the ports 1060.

In some embodiments, one or more of function calls of the SFE ports 1060can be to one or more service engines 1030 that process context-basedservice rules in the context-based service rule storages 1040. Eachservice engine 1030 in some embodiments has its own context-basedservice rule storage 1040, attribute-mapping storage 1023, andconnection state cache storage 1025. FIG. 10 presents just onecontext-based service rule storage 1040, attribute-mapping storage 1023,and connection state cache storage 1025 for all the service engines inorder not to obscure the presentation in this figure with unnecessarydetail. Also, in some embodiments, each VM can have its own instance ofa service engine (e.g., its own instance of encryption engine 1024, loadbalancer 1026, and firewall engine 1028). In other embodiments, oneservice engine can service data message flows for multiple VMs on a host(e.g., VMs for the same logical network).

To perform its service operation for a data message flow, a serviceengine 1030 in some embodiments tries to match the flow identifier(e.g., the five-tuple identifier) and/or the flow's associated contextattribute set to the rule identifiers of its service rules in itscontext-based service rule storage 1040. Specifically, for a serviceengine 1030 to perform its service check operation for a data messageflow, the SFE port 1060 that calls the service engine supplies a set ofattributes of a message that the port receives. In some embodiments, theset of attributes are message identifiers, such as traditionalfive-tuple identifiers. In some embodiments, one or more of theidentifier values can be logical values that are defined for a logicalnetwork (e.g., can be IP addresses defined in a logical address space).In other embodiments, all of the identifier values are defined in thephysical domains. In still other embodiments, some of the identifiervalues are defined in the logical domain, while other identifier valuesare defined in the physical domain.

The service engine in some embodiments then uses the received message'sattribute set (e.g., the message's five-tuple identifier) to identifythe context attribute set that the service engine has stored for thisflow in the attribute-mapping storage 1023. As mentioned above, thecontext engine 1050 in some embodiments supplies the context attributesfor new flows (i.e., new network connection events) to the serviceengines 1030, along with a flow identifier (e.g., a five-tupleidentifier). The context-engine policy storage 1043 contains the rulesthat control the operation of the context engine 1050. In someembodiments, these policies direct the context engine to generate rulesfor the service engines or to direct the service engines to generaterules. The service engines 1030 in these embodiments store the contextattributes that they receive from the context engine in theattribute-mapping storage 1023.

In some embodiments, a service engine 1030 stores the context attributeset for each new flow with that flow's identifier (e.g., five-tupleidentifier) in the attribute-mapping storage. In this manner, theservice engine can identify the context attribute set for each new flowthat it receives from the SFE ports 1060 by searching itsattribute-mapping storage 1023 for a context record that has a matchingflow identifier. The context record with the matching flow identifierincludes the context attribute set for this flow. Similarly, to identifythe context attribute set for a process event, a service engine in someembodiments searches its attribute-mapping storage 1023 for a contextrecord with a matching process identifier.

Some or all of the service engines in some embodiments pull the contextattribute sets for a new flow from the context engine. For instance, insome embodiments, a service engine supplies a new flow's five-tupleidentifier that it receives from the SFE port 1060, to the contextengine 1050. This engine 1050 then examines its attribute storage 1045to identify a set of attributes that is stored for this five-tupleidentifier, and then supplies this attribute set (or a subset of it thatit obtains by filtering the identified attribute set for the serviceengine) to the service engine.

Some embodiments implement the pull model by using a service token toencode the attribute set for a new message flow. When notified of a newnetwork connection event, the context engine 1050 in some embodiments(1) collects the context attribute set for the new event, (2) filtersthis set to discard the attributes that are not relevant for performingone or more services on the flow, (3) stores the remaining filteringattribute subset in the attribute storage 1045 along with a servicetoken, (4) provides the service token to the GI agent 1048. The GI agent1048 then causes this token to be passed to the service engine(s)in-band (e.g., in a header of the data message that the agent's VM sendsto a destination) or out-of-band (i.e., separately from the datamessages that the agent's VM sends to a destination).

When the service engine gets the new flow through the SFE port 1060, itsupplies this flow's service token to the context engine, which usesthis service token to identify in its attribute storage 1045 the contextattributes to supply to the service engine. In the embodiments that theSFE port does not provide this service token to the service engine, theservice engine first has to identify the service token by searching itsdata stores using the flow's identifier before supplying the servicetoken to the context engine.

After identifying the contextual attribute set for a data message flow,the service engine 1030 in some embodiments performs its serviceoperation based on service rules that are stored in the context-basedservice rule storage 1040. To perform its service operation, the serviceengine 1030 matches the received attribute subset with correspondingattribute sets that are stored for the service rules. In someembodiments, each service rule in the context-based service rule storage1040 has a rule identifier and an action parameter set.

As mentioned above, the rule identifier of a service rule in someembodiments can be defined in terms of one or more contextual attributesthat are not L2-L4 header parameters (e.g., are L7 parameters, useridentifiers, group identifiers, process name, loaded module identifiers,consumption parameters, etc.). In some embodiments, a rule identifiercan also include L2-L4 header parameters. Also, in some embodiments, oneor more parameters in a rule identifier can be specified in terms of anindividual value or a wildcard value. Also, in some embodiments, a ruleidentifier can include a set of individual values or a group identifier,such as a security group identifier, a compute construct identifier, anetwork construct identifier, etc.

To match a received attribute set with the rules, the service enginecompares the received attribute set with the associated identifiers ofthe service rules stored in the context-based service rule storage 1040.Upon identifying a matching rule, the service engine 1030 performs aservice operation (e.g., a service-orchestration operation, a firewalloperation, a load balancing operation, an encryption operation, othermiddlebox operation, etc.), based on the action parameter set (e.g.,based on the service action list, Allow/Drop parameters, the loadbalancing criteria, encryption parameters, etc.) of the matching rule.

In some embodiments, the context-based service rule storage 1040 isdefined in a hierarchical manner to ensure that a message rule checkwill match a higher priority rule before matching a lower priority rulewhen the message's attribute subset matches multiple rules. Also, insome embodiments, the context-based service rule storage 1040 contains adefault rule that specifies a default action for any message rule checkthat cannot identify any other service rules; this default rule will bea match for all possible attribute subsets in some embodiments, andensures that the service rule engine will return an action for allreceived attribute subsets. In some embodiments, the default rule willspecify no service.

Multiple messages can have the same message identifier attribute sets,e.g., when the messages are part of one flow that is associated with onecommunication session between two machines. Accordingly, after matchinga data message with a service rule in the context-based service rulestorage 1040 based on the message's identified context attribute set,the service engine of some embodiments stores the service rule (or areference to the service rule) in the connection state cache storage1025, so that it can later use this service rule for subsequent datamessages of the same flow.

In some embodiments, the connection state cache storage 1025 stores theservice rule, or a reference to the service rule, that the serviceengine 1030 identifies for different message identifier sets (e.g., fordifferent five-tuple identifiers that identify different data messageflows). In some embodiments, the connection state cache storage 1025stores each service rule, or reference to the service rule, with anidentifier (e.g., a flow's five-tuple identifier) that is generated fromthe matching message identifier set.

Before checking with the context-based service rule storage 1040 for aparticular message, the service rule engine 1030 of some embodimentschecks the connection state cache storage 1025 to determine whether thisstorage has previously identified a service rule for this message'sflow. If not, the service engine 1030 identifies the contextualattribute set for the message flow, and then checks the context-basedservice rule storage 1040 for a service rule that matches the message'sidentified attribute set and/or its five-tuple identifier. When theconnection state data storage has an entry for the particular message,the service engine performs its service operation based on this servicerule's action parameter set.

As mentioned above, a service node on a host computer in someembodiments is formed by (1) the software forwarding element 1010associated with the VTEP that serves as a Geneve tunnel endpoint, and(2) the service orchestrator 1022. For an ingress service node (e.g.,service node 120), the service orchestrator performs the operations ofthe process 800 of FIG. 8 in some embodiments. For instance, itretrieves the metadata captured by the context engine 1050 for aparticular data message flow. For a data message sent by a GVM 1005 onits host computer, the service orchestrator 1022 identifies the SFP listby matching the message's flow identifier and/or contextual metadataattributes to its service rule in the rule storage 1040.

In some embodiments, each of the orchestrator's service rule in thestorage 1040 specifies a service chain in terms of a list of IPaddresses (and in some cases a service tag descriptor) for each serviceoperation in the service chain. After matching the message's attributeset with one of its service rules, the service orchestrator 1022 of theingress node embeds the SFP list of the matching service rule in aGeneve tunnel header, along with other tunnel attributes described above(e.g., service index, etc.).

Also, in some embodiments, the orchestrator embeds some or all of themetadata obtained from the context engine 1050 in the NSH metadataoption TLV of the Geneve tunnel header. In some embodiments, the serviceorchestrator 1022 has another one of the service engines 1030 performthe tunnel encapsulation. After encapsulating the data message with aGeneve tunnel header 200, the service orchestrator returns the datamessage to the SFE (e.g., provides a handle for the location in memoryat which the encapsulated data message is stored) so that the SFE canforward the data message along the Geneve tunnel to the service nodeassociated with the first service machine in the specified SFP list.

In some cases, it is possible for the first service operation or thefirst few service operations to have to be performed by one or more SVMs1032 or service engines 1030 on the same host as the source GVM andingress service orchestrator. In these cases, the service orchestratordirects the data message to the SVM(s) or service engine(s) on its hostsbefore encapsulating the data message with a tunnel header. After allthe specified service operations have been performed on its hostcomputer, the service orchestrator in these cases then encapsulates theprocessed data message and directs the SFE to send this data message tothe service node associated with the next service operation in the SFPlist.

Also, for each data message flow, the ingress service orchestrator insome embodiments performs a load balancing operation to convert each VIPaddress that specifies a service operation in a matching service rule(i.e., a rule that matches the flow's identifiers and/or contextualmetadata) in the rule storage 1040 to a DIP address of a specificservice machine. The ingress service orchestrator does this so that itcan embed DIP addresses of actual service machines in the tunnel header,instead of VIP addresses of service machine clusters. Rather than doingthis load balancing itself, the service orchestrator uses the loadbalancing engine 1026 in some embodiments. Alternatively, in otherembodiments, the service orchestrator embeds one or more VIP address,and one of the service machines in the SFP list (e.g., the first servicemachine) is a load balancer that converts each VIP address to a DIPaddress.

When the service orchestrator is performing the operations of anon-ingress service node, the service orchestrator performs theoperations of the process 900 of FIG. 9 in some embodiments. Forinstance, it determines that a tunnel encapsulated data message has anSFP list that identifies an IP address of an SVM or service engineassociated with the orchestrator as the address of the next servicemachine. It decapsulates the Geneve tunnel header from a data messagethat is received along a Geneve tunnel, or directs another one of theservice engines 1030 to perform this decapsulation. The serviceorchestrator 1022 then stores the decapsulated tunnel information in thetunnel data storage 1075 for later re-use.

Once the received data message has been decapsulated and its tunnelinformation has been stored, the service orchestrator passes the datamessage, and in some cases, its metadata, to its associated SVM 1032 orservice engine 1030 on its host 1000 to perform the next serviceoperation. If multiple SVMs or service engines have to process the datamessage, the service orchestrator sequentially passes the data messageto each of its associated service machines that have to sequentiallyprocess the message. Each time the service orchestrator passes the datamessage to a service machine, it removes that machine's IP address fromthe SFP list or adjusts the service index, as mentioned above.

From one or more of its service machines, the service orchestrator canget metadata. Based on this metadata, the service orchestrator canperform re-classification operations to re-specify the SFP list in someembodiments. After having its associated service machine(s) process thedata message, the service orchestrator determines whether the SFP listis empty. If so, it provides the data message to one of the GVMs on itshost 1000 when the data message's destination is one of these GVMs. Whenthe data message's destination is not a GVM on its host computer, theservice orchestrator encapsulates the data message with a tunnel header(e.g., a Geneve tunnel header) and then provides the encapsulated datamessage to the SFE to send to its destination along a tunnel.

On the other hand, after processing a data message, and determining thatthe SFP list is not empty, the service orchestrator encapsulates thedata message with a Geneve tunnel header, in which it embeds themodified SFP list and service index along with other tunnel attributes(e.g., metadata, etc.). As described above, and further described belowby reference to FIG. 13, the service orchestrator in some embodimentscan embed in the NSH metadata option TLV of the Geneve tunnel headermetadata that was captured or generated by the orchestrator's associatedservice machine as this machine was processing the data message. Theservice orchestrator provides the encapsulated data message to the SFEto send along a Geneve tunnel to the service node of the next servicemachine identified in the SFP list.

FIG. 11 illustrates an example of how the service orchestrators 1022 aremanaged in some embodiments. This figure illustrates multiple hosts 1000in a datacenter. As shown, each host includes several service engines1030, a context engine 1050, a service orchestrator 1022, several GVMs1005, one or more SVMs 1032 and an SFE 1010.

It also illustrates a set of controllers 1105 for managing the serviceorchestrators 1022 and the service engines 1030, GVMs 1005, and SFEs1010. The hosts and controllers communicatively connect to each otherthrough a network 1110, which can be a local area network, a wide areanetwork, a network of networks (such as the Internet), etc. Thecontroller set provides a user interface for the administrators todefine context-based service rules in terms of contextual attributes,and communicates with the hosts through the network 1110 to providethese policies.

In some embodiments, the context engines 1050 collect contextualattributes that are passed to the management servers in the controllerset through a network 1110 so that these contextual attributes can beused to define policies. The management servers in some embodimentsinteract with the discovery engines executing on the host computers 1000in the datacenter to obtain and refresh inventory of all processes andservices that are running on the GVMs on the hosts. The management planein some embodiments then provides a rule creation interface for allowingadministrators to create context-based service rules for the serviceengines, SVMs and the orchestrating engines 1022.

Once the high-level service policies are defined in the managementplane, the management plane directly supplies some or all of thesepolicies to the management proxies (not shown) on the hosts 1000, and/orindirectly supplies some or all of these policies to these proxiesthrough a set of configuring controllers. In some embodiments, themanagement proxies publish the received policies as rules to thecontext-based service rule storages 1043. In some embodiments, theproxies transform these policies before publishing them to thecontext-based service rule storages 1043. Also, the context engines 1050on the hosts 1000 in some embodiments resolve the policies based oncollected contextual attributes, in order to generate rules for theservice engines.

In some embodiments, different policies are specified for different datamessage flows from a source GVM based on different traffic contentcarried by these flows. For instance, one policy might define an SFPlist that use low-latency service engines for a data message flow from asource GVM that is for a video conference involving the executive staffof a corporation, while another policy might define an SFP list thatuses service engines with higher latency for a data message flow fromthe same GVM when this message flow pertains to an email being sent.

FIGS. 12 and 13 illustrate two examples for forwarding and processingmetadata in connection with service operations that are performed byservice machines in some embodiments. The example illustrated in FIG. 12shows the processing of two message flows 1202 and 1204 that emanatefrom one VM 1205 on a host 1210 at two different times. Both thesemessage flows need to be processed by firewall service machines, and aredirected to one firewall machine in one of two firewall service clusters1230 and 1232 by a load balancing SVM 1220 executing on another host1225.

The ingress service node 1212 of the first host 1210 encapsulates thedata messages for both of these flows with a tunnel header that includescontextual metadata about the data message flow. The contextual metadatafor the first flow 1202 specifies that this flow carries videoconference data for someone on the executive staff (Estaff) of thecompany, while the contextual metadata for the second flow 1204specifies that this flow carries email data for someone in HumanResource (HR) Department. The HR and Estaff information is expressed interms of active directory group identifiers in some embodiments. Also,in some embodiments, the ingress service node 1212 stores the contextualmetadata in each data message of each flow, while in other embodimentsthe ingress service node stores the contextual metadata only in a subsetof the data messages (e.g., the first message, or the first N messages,or every 100 messages) of each flow.

The service node 1222 of the host 1225 decapsulates each encapsulateddata message, and provides to the load balancing SVM 1220 thedecapsulated data message along with the embedded contextual metadataattributes, which indicate the traffic type and active directory groupidentifier. Based on the contextual metadata attributes, the loadbalancer 1220 determines that the first data message flow has to bedirected to the low-latency firewall service cluster 1230, while thesecond data message flow 1204 can be directed to the regular firewallservice cluster 1232.

For each message flow, the load balancer 1220 also selects one firewallservice machine 1250 or 1252 in each service cluster 1230 or 1232, andprovides the selected firewall service machine's identifier (e.g., itsIP address) to the service node 1222. Based on the provided servicemachine identifiers, the service node 1222 then forwards each datamessage flow to the firewall machines 1250 or 1252 that the loadbalancer 1220 selected for each flow.

FIG. 13 illustrates a similar example to that of FIG. 12, except that inFIG. 13, the ingress service node 1312 does not identify the traffictype but rather leaves the traffic-type identification to a DPI servicemodule 1370 that executes on a host computer 1375 along with the firstservice node 1372. In some embodiments, the DPI service module 1370identifies the traffic type by examining the first data message or firstfew data messages in each flow using standard DPI techniques.

After identifying the traffic type, the DPI module generates atraffic-type identifier, and provides this generated metadata to thefirst service node 1372. After receiving this metadata for a datamessage, the first service node 1372 then re-encapsulates the datamessage with a tunnel header that includes both the active-directorymetadata received from the ingress service node 1312 and the traffictype metadata generated by the DPI module 1370. The first service node1372 then forwards each encapsulated data message of each flow to theservice node 1222 of the host 1225. The service node 1222 in FIG. 13then processes each data message flow in the same way as the servicenode 1222 of FIG. 12.

Many of the above-described features and applications are implemented assoftware processes that are specified as a set of instructions recordedon a computer readable storage medium (also referred to as computerreadable medium). When these instructions are executed by one or moreprocessing unit(s) (e.g., one or more processors, cores of processors,or other processing units), they cause the processing unit(s) to performthe actions indicated in the instructions. Examples of computer readablemedia include, but are not limited to, CD-ROMs, flash drives, RAM chips,hard drives, EPROMs, etc. The computer readable media does not includecarrier waves and electronic signals passing wirelessly or over wiredconnections.

In this specification, the term “software” is meant to include firmwareresiding in read-only memory or applications stored in magnetic storage,which can be read into memory for processing by a processor. Also, insome embodiments, multiple software inventions can be implemented assub-parts of a larger program while remaining distinct softwareinventions. In some embodiments, multiple software inventions can alsobe implemented as separate programs. Finally, any combination ofseparate programs that together implement a software invention describedhere is within the scope of the invention. In some embodiments, thesoftware programs, when installed to operate on one or more electronicsystems, define one or more specific machine implementations thatexecute and perform the operations of the software programs.

FIG. 14 conceptually illustrates a computer system 1400 with which someembodiments of the invention are implemented. The computer system 1400can be used to implement any of the above-described hosts, controllers,and managers. As such, it can be used to execute any of the abovedescribed processes. This computer system includes various types ofnon-transitory machine readable media and interfaces for various othertypes of machine readable media. Computer system 1400 includes a bus1405, processing unit(s) 1410, a system memory 1425, a read-only memory1430, a permanent storage device 1435, input devices 1440, and outputdevices 1445.

The bus 1405 collectively represents all system, peripheral, and chipsetbuses that communicatively connect the numerous internal devices of thecomputer system 1400. For instance, the bus 1405 communicativelyconnects the processing unit(s) 1410 with the read-only memory 1430, thesystem memory 1425, and the permanent storage device 1435.

From these various memory units, the processing unit(s) 1410 retrieveinstructions to execute and data to process in order to execute theprocesses of the invention. The processing unit(s) may be a singleprocessor or a multi-core processor in different embodiments. Theread-only-memory (ROM) 1430 stores static data and instructions that areneeded by the processing unit(s) 1410 and other modules of the computersystem. The permanent storage device 1435, on the other hand, is aread-and-write memory device. This device is a non-volatile memory unitthat stores instructions and data even when the computer system 1400 isoff. Some embodiments of the invention use a mass-storage device (suchas a magnetic or optical disk and its corresponding disk drive) as thepermanent storage device 1435.

Other embodiments use a removable storage device (such as a flash drive,etc.) as the permanent storage device. Like the permanent storage device1435, the system memory 1425 is a read-and-write memory device. However,unlike storage device 1435, the system memory is a volatileread-and-write memory, such a random access memory. The system memorystores some of the instructions and data that the processor needs atruntime. In some embodiments, the invention's processes are stored inthe system memory 1425, the permanent storage device 1435, and/or theread-only memory 1430. From these various memory units, the processingunit(s) 1410 retrieve instructions to execute and data to process inorder to execute the processes of some embodiments.

The bus 1405 also connects to the input and output devices 1440 and1445. The input devices enable the user to communicate information andselect commands to the computer system. The input devices 1440 includealphanumeric keyboards and pointing devices (also called “cursor controldevices”). The output devices 1445 display images generated by thecomputer system. The output devices include printers and displaydevices, such as cathode ray tubes (CRT) or liquid crystal displays(LCD). Some embodiments include devices such as a touchscreen thatfunction as both input and output devices.

Finally, as shown in FIG. 14, bus 1405 also couples computer system 1400to a network 1465 through a network adapter (not shown). In this manner,the computer can be a part of a network of computers (such as a localarea network (“LAN”), a wide area network (“WAN”), or an Intranet, or anetwork of networks, such as the Internet. Any or all components ofcomputer system 1400 may be used in conjunction with the invention.

Some embodiments include electronic components, such as microprocessors,storage and memory that store computer program instructions in amachine-readable or computer-readable medium (alternatively referred toas computer-readable storage media, machine-readable media, ormachine-readable storage media). Some examples of such computer-readablemedia include RAM, ROM, read-only compact discs (CD-ROM), recordablecompact discs (CD-R), rewritable compact discs (CD-RW), read-onlydigital versatile discs (e.g., DVD-ROM, dual-layer DVD-ROM), a varietyof recordable/rewritable DVDs (e.g., DVD-RAM, DVD-RW, DVD+RW, etc.),flash memory (e.g., SD cards, mini-SD cards, micro-SD cards, etc.),magnetic and/or solid state hard drives, read-only and recordableBlu-Ray® discs, ultra-density optical discs, and any other optical ormagnetic media. The computer-readable media may store a computer programthat is executable by at least one processing unit and includes sets ofinstructions for performing various operations. Examples of computerprograms or computer code include machine code, such as is produced by acompiler, and files including higher-level code that are executed by acomputer, an electronic component, or a microprocessor using aninterpreter.

While the above discussion primarily refers to microprocessor ormulti-core processors that execute software, some embodiments areperformed by one or more integrated circuits, such as applicationspecific integrated circuits (ASICs) or field programmable gate arrays(FPGAs). In some embodiments, such integrated circuits executeinstructions that are stored on the circuit itself.

As used in this specification, the terms “computer”, “server”,“processor”, and “memory” all refer to electronic or other technologicaldevices. These terms exclude people or groups of people. For thepurposes of the specification, the terms display or displaying meansdisplaying on an electronic device. As used in this specification, theterms “computer readable medium,” “computer readable media,” and“machine readable medium” are entirely restricted to tangible, physicalobjects that store information in a form that is readable by a computer.These terms exclude any wireless signals, wired download signals, andany other ephemeral or transitory signals.

While the invention has been described with reference to numerousspecific details, one of ordinary skill in the art will recognize thatthe invention can be embodied in other specific forms without departingfrom the spirit of the invention. For instance, several figuresconceptually illustrate processes. The specific operations of theseprocesses may not be performed in the exact order shown and described.The specific operations may not be performed in one continuous series ofoperations, and different specific operations may be performed indifferent embodiments. Furthermore, the process could be implementedusing several sub-processes, or as part of a larger macro process.

The above-described methodology is used in some embodiments to expressservice chains in single tenant environments. Thus, one of ordinaryskill will realize that some embodiments of the invention are equallyapplicable to single tenant datacenters. Conversely, in someembodiments, the above-described methodology is used to carry servicechain specification across different datacenters of different datacenterproviders when one entity (e.g., one corporation) is a tenant inmultiple different datacenters of different providers. In theseembodiments, the tenant identifiers that are embedded in the tunnelheaders have to be unique across the datacenters, or have to betranslated when they traverse from one datacenter to the next. Thus, oneof ordinary skill in the art would understand that the invention is notto be limited by the foregoing illustrative details, but rather is to bedefined by the appended claims

The invention claimed is:
 1. A method of specifying service operationsfor a data message associated with a particular machine, the methodcomprising: in a first option TLV (type, length, and value) portion of aGeneve tunnel header for encapsulating a data message, storing aplurality of service identifiers associated with a plurality of servicemachines for performing a plurality of service operations on the datamessage; in a metadata second option TLV portion of the Geneve tunnelheader, storing a set of metadata for use by at least a subset of one ormore service machines to perform at least a subset of one or moreservice operations on the data message based on at least one storedmetadata, wherein the first and second option TLV portions are differentTLV portions of the Geneve tunnel header; and forwarding the datamessage encapsulated with the Geneve tunnel header along a tunnel to afirst service machine to perform a first service operation identified bythe plurality of service identifiers.
 2. The method of claim 1, whereinthe metadata is stored in the metadata second option TLV portion in anetwork service header (NSH) metadata format.
 3. The method of claim 1,wherein the metadata comprises contextual metadata that relates to thedata message and that is captured at a host computer on which theparticular machine executes.
 4. The method of claim 3 furthercomprising: through a guest introspection agent installed on theparticular machine, receiving a set of contextual metadata attributesfor the data message flow; and associating the set of contextualmetadata attributes with the data message before forwarding theencapsulated data message along the tunnel to the first service machine.5. The method of claim 1, wherein at least one service machineidentified by one service identifier provides at least one additionalmetadata attribute to store in the metadata second option TLV portionfor processing by at least one other service machine identified byanother service identifier.
 6. The method of claim 1, wherein storingthe plurality of service identifiers comprises storing in the tunnelheader a plurality of network addresses of the plurality of servicemachines.
 7. The method of claim 1, wherein the tunnel connects to afirst service node that connects to the first service machine withouthaving to utilize any intervening hardware router or hardware switch. 8.The method of claim 7, wherein the first service machine is one of astandalone computer, a service module executing on a host computer, anda standalone service appliance.
 9. The method of claim 7, wherein thefirst service node and first service machine are modules executing on ahost computer along with other machines.
 10. The method of claim 7,wherein the first service node removes the tunnel header, provides thedata message to the first service machine along with at least one storedmetadata attribute, receives the processed data message from the firstservice machine, encapsulates the processed data message with anothertunnel header generated from information obtained from the removedtunnel header, stores at least one metadata attribute in the generatedtunnel header and sends the encapsulated processed data message alonganother tunnel to another service node that is connected to a secondservice machine to perform a second service operation identified by theplurality of service identifiers.
 11. A non-transitory machine readablemedium storing a program for specifying service operations for a datamessage associated with a source machine, the program for execution byat least one processing unit of a host computer on which a sourcemachine executes, the program comprising sets of instructions for:identifying, through a guest introspection agent operating on the sourcemachine, a set of contextual metadata for a data message flow emanatingfrom the source machine; in a first option TLV (type, length, and value)portion of a Geneve tunnel header for encapsulating a data message ofthe data message flow, storing a plurality of network addresses of aplurality of service machines that are to perform a plurality of serviceoperations on the data message; in a metadata second option TLV portionof the Geneve tunnel header, storing the set of contextual metadata foruse by at least a subset of one or more service machines to perform atleast a subset of one or more service operations on the data messagebased on at least one stored contextual metadata set, wherein the firstand second option TLV portions are different TLV portions of the Genevetunnel header; and forwarding the data message encapsulated with theGeneve tunnel header along a Geneve tunnel to a first service machine toperform a first service operation identified by the plurality of serviceidentifiers.
 12. The non-transitory machine readable medium of claim 11,wherein the contextual metadata is stored in the metadata second optionTLV portion in a network service header (NSH) metadata format.
 13. Thenon-transitory machine readable medium of claim 11, wherein the metadatacomprises contextual metadata that relates to the data message and thatis captured at a host computer on which the source machine executes. 14.The non-transitory machine readable medium of claim 13, wherein the setof instructions for identifying the set of contextual metadata programfurther comprises sets of instructions for: through the guestintrospection agent installed on the source machine, receiving a set ofcontextual metadata attributes for the data message flow; andassociating the set of contextual metadata attributes with the datamessage before forwarding the encapsulated data message along the tunnelto the first service machine.
 15. The non-transitory machine readablemedium of claim 11, wherein at least one service machine identified byone service identifier provides at least one additional contextualmetadata attribute to store in the metadata second option TLV portionfor processing by at least one other service machine identified byanother service identifier.
 16. The non-transitory machine readablemedium of claim 11, wherein the set of instructions for storing theplurality of service identifiers comprises a set of instructions forstoring in the tunnel header a plurality of network addresses of theplurality of service machines.
 17. The non-transitory machine readablemedium of claim 11, wherein the tunnel connects to a first service nodethat connects to the first service machine without having to utilize anyintervening hardware router or hardware switch.
 18. The non-transitorymachine readable medium of claim 17, wherein the first service machineis one of a standalone computer, a service module executing on a hostcomputer, and a standalone service appliance.
 19. The non-transitorymachine readable medium of claim 17, wherein the first service node andfirst service machine are modules executing on a host computer alongwith other machines.
 20. The non-transitory machine readable medium ofclaim 11, wherein the service operations are middlebox serviceoperations.
 21. The non-transitory machine readable medium of claim 11,wherein metadata second option TLV portion is selectively definable as afixed-sized metadata portion or a variable-sized metadata portion.